Markup fixes.

        * gdk-pixbuf/tmpl/creating.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-from-drawables.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-init.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-rendering.sgml,
        gdk-pixbuf/tmpl/refcounting.sgml: Markup fixes.

        * gtk/building.sgml, gtk/resources.sgml: Markup fixes.

        * gtk/gtk.types: Remove gtk_text_layout_get_type(). (???)

        * gdk/tmpl/general.sgml: Use <envar>, not <envvar>.

        * gdk-pixbuf-io.c, gdk-pixbuf-animation.c, gdk-pixbuf-data.c,
        gdk-pixbuf-loader.c, gdk-pixbuf-scale.c, gdk-pixbuf-util.c,
        gdk-pixdata.c: Markup fixes.

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index cf1124a25d27cb8d19764318a15eff9295984b76..151d618baa3d41c00fec7e8c19be2ebb71c5fa8d 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,21 @@
+2001-12-17  Matthias Clasen  <matthiasc@poet.de>
+
+       * gdk-pixbuf/tmpl/creating.sgml, 
+       gdk-pixbuf/tmpl/gdk-pixbuf-xlib-from-drawables.sgml,
+       gdk-pixbuf/tmpl/gdk-pixbuf-xlib-init.sgml,
+       gdk-pixbuf/tmpl/gdk-pixbuf-xlib-rendering.sgml,
+       gdk-pixbuf/tmpl/refcounting.sgml: Markup fixes.
+
+       * gtk/building.sgml, gtk/resources.sgml: Markup fixes.
+
+       * gtk/gtk.types: Remove gtk_text_layout_get_type(). (???)
+
+       * gdk/tmpl/general.sgml: Use <envar>, not <envvar>.
+
+2001-12-16  Matthias Clasen  <matthiasc@poet.de>
+
+       * gdk/tmpl/windows.sgml: Document GDK_RELEASE_MASK.
+
 2001-12-16  Havoc Pennington  <hp@pobox.com>
 
        * gdk-pixbuf/gdk-pixbuf-sections.txt: put _simple variants at the

diff --git a/docs/reference/gdk/tmpl/general.sgml b/docs/reference/gdk/tmpl/general.sgml
index f1a17109b81f332a50b26d29e2dfc309d3771e56..bd20b4cbff72e606c0bc8ded995cb2b1be768b6e 100644 (file)
--- a/docs/reference/gdk/tmpl/general.sgml
+++ b/docs/reference/gdk/tmpl/general.sgml
@@ -60,7 +60,7 @@ system call. This function is called by gtk_set_locale() and so GTK+
 applications should use that instead.
 </para>
 <para>
-The locale to use is determined by the <envvar>LANG</envvar> environment variable,
+The locale to use is determined by the <envar>LANG</envar> environment variable,
 so to run an application in a certain locale you can do something like this:
 <informalexample>
 <programlisting>
@@ -134,7 +134,7 @@ Sets the program class.
 
 <!-- ##### FUNCTION gdk_get_display ##### -->
 <para>
-Gets the name of the display, which usually comes from the <envvar>DISPLAY</envvar>
+Gets the name of the display, which usually comes from the <envar>DISPLAY</envar>
 environment variable or the <option>--display</option> command line option.
 </para>
 

diff --git a/docs/reference/gdk/tmpl/windows.sgml b/docs/reference/gdk/tmpl/windows.sgml
index c8a350c73847908461a061307d6eb71f3c1f32e7..177f4703c4d35a427072c2208d26c6cf1ef19fd3 100644 (file)
--- a/docs/reference/gdk/tmpl/windows.sgml
+++ b/docs/reference/gdk/tmpl/windows.sgml
@@ -1043,7 +1043,8 @@ Like the X Window System, GDK supports 8 modifier keys and 5 mouse buttons.
 @GDK_BUTTON3_MASK: the third mouse button. 
 @GDK_BUTTON4_MASK: the fourth mouse button.
 @GDK_BUTTON5_MASK: the fifth mouse button.
-@GDK_RELEASE_MASK: 
+@GDK_RELEASE_MASK: not used in GDK itself. GTK+ uses it to differentiate 
+  between (keyval, modifiers) pairs from key press and release events. 
 @GDK_MODIFIER_MASK: 
 
 <!-- ##### FUNCTION gdk_window_get_parent ##### -->

diff --git a/docs/reference/gtk/building.sgml b/docs/reference/gtk/building.sgml
index 9b6541ec04fd5ed64655b94c78477b5f9cc277c4..4f47b2c030c6fbf862de1e7975f8e02fdd1b1679 100644 (file)
--- a/docs/reference/gtk/building.sgml
+++ b/docs/reference/gtk/building.sgml
@@ -111,7 +111,8 @@ How to compile GTK+ itself
          <application>gtk-doc</application> package is installed.  If
          it is, then it will use it to extract and build the
          documentation for the GTK+ library.  These options
-         can be used to explicitly control whether gtk-doc should be
+         can be used to explicitly control whether 
+          <application>gtk-doc</application> should be
          used or not.  If it is not used, the distributed,
          pre-generated HTML files will be installed instead of
          building them on your machine.

diff --git a/docs/reference/gtk/gtk.types b/docs/reference/gtk/gtk.types
index 665164bd4f085d7e86897a80a79e4067439023c6..06ff655e06000acfcd9a0f4dd618258de5856ef0 100644 (file)
--- a/docs/reference/gtk/gtk.types
+++ b/docs/reference/gtk/gtk.types
@@ -95,7 +95,6 @@ gtk_tearoff_menu_item_get_type
 gtk_text_buffer_get_type
 gtk_text_child_anchor_get_type
 gtk_text_get_type
-gtk_text_layout_get_type
 gtk_text_mark_get_type
 gtk_text_tag_get_type
 gtk_text_tag_table_get_type

diff --git a/docs/reference/gtk/resources.sgml b/docs/reference/gtk/resources.sgml
index 5a6410c1f7b3dabd5c6326cced1e963c097343c6..bd49b948dfc2ae8f11c573a5c838e54c5e959429 100644 (file)
--- a/docs/reference/gtk/resources.sgml
+++ b/docs/reference/gtk/resources.sgml
@@ -17,9 +17,10 @@ Getting help with GTK+
 
 <para>
 If you encounter a bug, misfeature, or missing feature in GTK+, please
-file a bug report on http://bugzilla.gnome.org. We'd also appreciate
-reports of incomplete or misleading information in the GTK+
-documentation; file those against the "docs" component of the "gtk+"
+file a bug report on 
+<ulink url="http://bugzilla.gnome.org">http://bugzilla.gnome.org</ulink>. 
+We'd also appreciate reports of incomplete or misleading information in 
+the GTK+ documentation; file those against the "docs" component of the "gtk+"
 product in Bugzilla.
 </para>
 
@@ -32,7 +33,7 @@ discussed, we'll add a note to that effect in the report.
 
 <para>
 The bug tracker should definitely be used for feature requests, it's
-not only for bugs. We track all GTK+ development in bugzilla, so it's
+not only for bugs. We track all GTK+ development in Bugzilla, so it's
 the way to be sure the GTK+ developers won't forget about an issue.
 </para>
 
@@ -44,17 +45,17 @@ the way to be sure the GTK+ developers won't forget about an issue.
 <para>
 If you develop a bugfix or enhancement for GTK+, please file that in
 Bugzilla as well. Bugzilla allows you to attach files; please attach a
-patch generated by the "diff" utility, using the "-u" option to make
-the patch more readable. All patches must be offered under the terms
-of the GNU LGPL license, so be sure you are authorized to give us the
-patch under those terms.
+patch generated by the <command>diff</command> utility, using the 
+<option>-u</option> option to make the patch more readable. All patches 
+must be offered under the terms of the GNU LGPL license, so be sure you 
+are authorized to give us the patch under those terms.
 </para>
 
 <para>
 If you want to discuss your patch before or after developing it, mail 
-gtk-devel-list@gnome.org. But be sure to file the Bugzilla report as
-well; if the patch is only on the list and not in Bugzilla, it's
-likely to slip through the cracks.
+<ulink url="mail:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink>. 
+But be sure to file the Bugzilla report as well; if the patch is only on the 
+list and not in Bugzilla, it's likely to slip through the cracks.
 </para>
 
 </refsect1>
@@ -66,7 +67,8 @@ likely to slip through the cracks.
 There are several mailing lists dedicated to GTK+ and related
 libraries. Discussion of GLib, Pango, and ATK in addition to GTK+
 proper is welcome on these lists. You can subscribe or view the
-archives of these lists on http://mail.gnome.org.
+archives of these lists on 
+<ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>.
 </para>
 
 <para>
@@ -113,8 +115,9 @@ all on topic.
 <varlistentry>
 <term>gtk-doc-list@gnome.org</term>
 <listitem><para>
-gtk-doc-list is for discussion of the gtk-doc documentation system
-(used to document GTK+), and for work on the GTK+ documentation.
+gtk-doc-list is for discussion of the <application>gtk-doc</application> 
+documentation system (used to document GTK+), and for work on the GTK+ 
+documentation.
 </para></listitem>
 </varlistentry>